<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">
 <head>
  <meta content="Copyright &copy; 2023 Thales. All Rights Reserved." name="copyright"/>
  <meta content="text/html;charset=utf-8" http-equiv="content-type"/>
  <meta content="text/css" http-equiv="Content-Style-Type"/>
  <title>
   Arcadia Reference - The Interface Trip
  </title>
  <link href="../../scripts/jquery-treeview/jquery.treeview.css" rel="stylesheet"/>
  <script src="../../scripts/jquery-treeview/lib/jquery-1.11.1.js" type="text/javascript">
  </script>
  <script src="../../scripts/jquery-treeview/jquery.treeview.js" type="text/javascript">
  </script>
  <link href="../../css/simpletree.css" rel="stylesheet" type="text/css"/>
  <link href="../../css/content.css" media="screen, projection" rel="stylesheet" title="default" type="text/css"/>
  <style>
   body {}
			.treeview {
				background-color: white ;
			}
	
			.treeview ul{ /*CSS for Simple Tree Menu*/
				background-color: white;
				font-size: 12px;
			}
	
			.treeview li{ /*Style for LI elements in general (excludes an LI that contains sub lists)*/
				background-color: white;
			}
  </style>
 </head>
 <body>
  <img src="../icon/logo_arcadia_small.png" style="float:left;width:50px;height:50px;"/>
  <nav>
   <a href="1a79525b3b624a7094acd0b580842ce6.html#">
    ARCADIA
   </a>
   <a href="1a79525b3b624a7094acd0b580842ce6.html#landscape">
    Engineering Landscape
   </a>
   <a href="1a79525b3b624a7094acd0b580842ce6.html#userGuide">
    User Guide
   </a>
   <a href="1a79525b3b624a7094acd0b580842ce6.html#reference">
    Reference Manual
   </a>
  </nav>
  <p>
   <br/>
  </p>
  <div id="content">
   <img alt="FunctionalChain" src="../icon/FunctionalChain.png" style="float:left; margin-right:10px"/>
   <h1>
    <a href="../ARCADIA/acdab1064f694b2882a59b4a7fd9f8ca.html">
     The Interface Trip
    </a>
   </h1>
   <p style="margin-top:3px; margin-bottom:3px">
    <span class="elementMetaClass">
     Engineering Process
    </span>
    <p>
    </p>
   </p>
   <em class="elementPath">
    <a href="../ARCADIA/ad8c8a109fa64f039584c15108639254.html">
     Engineering Capabilities
    </a>
    &gt;
    <a href="../ARCADIA/69960d428e0340028c120c059f5c9910.html">
     Define a Solution satisfying Need
    </a>
    &gt;
    <a href="../ARCADIA/acdab1064f694b2882a59b4a7fd9f8ca.html">
     The Interface Trip
    </a>
   </em>
   <p>
    <p>
     <strong>
      Challenge: How to build, justify and allocate internal and external&nbsp;interfaces to sub-systems and components
     </strong>
     .
    </p>
    <ul>
     <li>
      Check consistency of&nbsp;imposed&nbsp;external interfaces description, and system need/solution definition
     </li>
     <li>
      Build and justify internal interfaces definition upon functional analysis, exchanges, functional chains etc.
     </li>
     <li>
      Enforce compliance of sub-systems/SW/HW parts with these interface through automatic generation of their requirements and interfaces definitions
     </li>
    </ul>
   </p>
   <h2>
    Related Diagrams
   </h2>
   <div>
    <p class="diagram-name" id="_0unrwJT3Eeqxb5_tqwKmHg">
     3  The Interface Trip
    </p>
    <p class="diagram">
     <img alt="3  The Interface Trip" src="acdab1064f694b2882a59b4a7fd9f8ca/_0unrwJT3Eeqxb5_tqwKmHg.jpg" usemap="#3  The Interface Trip__0unrwJT3Eeqxb5_tqwKmHg_PositionMap"/>
     <br/>
     <br/>
     <map name="3  The Interface Trip__0unrwJT3Eeqxb5_tqwKmHg_PositionMap">
      <area alt="e8a6129c560e4e5699f785edb67049e9" coords="750,253,850,303" group="e8a6129c560e4e5699f785edb67049e9" href="../ARCADIA/e8a6129c560e4e5699f785edb67049e9.html#ide8a6129c-560e-4e56-99f7-85edb67049e9" shape="rect"/>
      <area alt="c354668558fc433fa1124e7b02e6bc7f" coords="10,138,110,188" group="c354668558fc433fa1124e7b02e6bc7f" href="../ARCADIA/c354668558fc433fa1124e7b02e6bc7f.html#idc3546685-58fc-433f-a112-4e7b02e6bc7f" shape="rect"/>
      <area alt="0f400333e4604c16a797eb161de26e50" coords="750,143,850,193" group="0f400333e4604c16a797eb161de26e50" href="../ARCADIA/0f400333e4604c16a797eb161de26e50.html#id0f400333-e460-4c16-a797-eb161de26e50" shape="rect"/>
      <area alt="b4f96ce88e5d4a75a44982269ade639f" coords="750,33,850,83" group="b4f96ce88e5d4a75a44982269ade639f" href="../ARCADIA/b4f96ce88e5d4a75a44982269ade639f.html#idb4f96ce8-8e5d-4a75-a449-82269ade639f" shape="rect"/>
      <area alt="21963be2f5f544798045079ed00879fa" coords="480,123,580,203" group="21963be2f5f544798045079ed00879fa" href="../ARCADIA/21963be2f5f544798045079ed00879fa.html#id21963be2-f5f5-4479-8045-079ed00879fa" shape="rect"/>
      <area alt="38c7424f5c11476490db367b0b43bc42" coords="230,138,330,188" group="38c7424f5c11476490db367b0b43bc42" href="../ARCADIA/38c7424f5c11476490db367b0b43bc42.html#id38c7424f-5c11-4764-90db-367b0b43bc42" shape="rect"/>
     </map>
    </p>
    <p class="diagram-description">
     <p>
      This figure describes
      <span>
       <span contenteditable="false" style="margin: 0px; padding: 0px; left: 0px; top: 137.79px; height: 0px; right: 0px; color: rgb(255, 255, 255); line-height: 0px; font-size: 0px; border-top-color: rgb(255, 0, 0); border-top-width: 1px; border-top-style: dashed; display: block; position: absolute; z-index: 9999;" unselectable="on">
        <span style="border-width: 8px 8px 8px 0px; border-style: solid; border-color: transparent rgb(255, 0, 0) transparent transparent; margin: 0px; padding: 0px; top: -8px; width: 0px; height: 0px; right: 0px; color: rgb(255, 255, 255); line-height: 0px; font-size: 0px; display: block; position: absolute; z-index: 9999;" unselectable="on">
         &nbsp;
        </span>
        <span style="border-width: 8px 0px 8px 8px; border-style: solid; border-color: transparent transparent transparent rgb(255, 0, 0); margin: 0px; padding: 0px; left: 0px; top: -8px; width: 0px; height: 0px; color: rgb(255, 255, 255); line-height: 0px; font-size: 0px; display: block; position: absolute; z-index: 9999;" unselectable="on">
         &nbsp;
        </span>
        <span contenteditable="false" style='background: url("file:///C:/Users/T0027549/MyApp/Capella%205.2/plugins/org.eclipse.nebula.widgets.richtext_1.2.0.201711021145/org/eclipse/nebula/widgets/richtext/resources/ckeditor/plugins/magicline/images/icon.png?t=F0RD") no-repeat center rgb(255, 0, 0); margin: 0px; padding: 0px; border-radius: 2px; top: -8px; width: 17px; height: 17px; right: 17px; color: rgb(255, 255, 255); line-height: 0px; font-size: 0px; display: block; position: absolute; z-index: 9999; cursor: pointer; -ms-border-radius: 2px;' title="Ins&eacute;rez un paragraphe ici" unselectable="on">
         &crarr;
        </span>
       </span>
      </span>
     </p>
     <p>
      <strong>
       How to build, justify and allocate internal and external&nbsp;interfaces to sub-systems and components
      </strong>
      .
     </p>
     <ul>
      <li>
       Check consistency of&nbsp;imposed&nbsp;external interfaces description, and system need/solution definition
      </li>
      <li>
       Build and justify internal interfaces definition upon functional analysis, exchanges, functional chains etc.
      </li>
      <li>
       Enforce compliance of sub-systems/SW/HW parts with these interface through automatic generation of their requirements and interfaces definitions
      </li>
     </ul>
     <p>
      For each step of this process, involving an engineering task or activity, the description gives some hints and methological recommendations. These recommendations are complementary with the description of the involved activity per se, in the context of the engineering concern and the process.
     </p>
    </p>
   </div>
   <h2>
    Contribution of each engineering activity to this process
   </h2>
   <table>
    <tr>
     <th>
      Engineering activity
     </th>
     <th>
      Specifics of activity for this process
     </th>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/c354668558fc433fa1124e7b02e6bc7f.html">
       Perform SYSTEM NEED ANALYSIS
      </a>
     </td>
     <td>
      <p>
       From the Interface Maangement point of view, Need Analysis mainly focuses on checking compatibility of external interfaces between the system of interest and other systems or actors.
      </p>
      <p>
       For each external system whose interface is imposed, check that all functions, functional chains and scenarios allocated to the system have corresponding elements in the external system interface definition : exchanged elements and data, time-related protocols if any, performance or non-functional constraints, etc. Update function, functional chains and scenarios definition if needed.
      </p>
      <p>
       From system users / operators point of view, similarly capture their expectations in terms of nature of expected interactions with the system, state-of-the-art practices, preferred modalities, expected information delivery, eetc.
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/38c7424f5c11476490db367b0b43bc42.html">
       Design PHYSICAL ARCHITECTURE
      </a>
     </td>
     <td>
      <p>
       Internal interfaces definition (and external interfaces not imposed by the customer, including user interfaces) is based on functional analysis of the solution architecture.
      </p>
      <p>
       The solution functional analysis describes its designed behaviour in terms of functions and their interactions/functional exchanges, functional chains and scenarios defining the way these functions and exchanges are involved in given situations, capabilities etc. Elements exchanged are also defined in terms of&nbsp;structure, contents, data.
      </p>
      <p>
       The architecture building process allocates functions to system components, and to external systems/actors/users. Therefore, the nature and contents&nbsp;of interfaces between solution components (internal interfaces) and external systems/users (external interfaces) are fully defined by the functional exchanges at boundaries of each component, along with their contents and dynamic behaviour from functional chains and scenarios.
      </p>
      <p>
       This conceptual, functional&nbsp;interface definition can then be optimised from an implementation and design point of view (e.g. by grouping exchanges, structuring exchange contents, adding technology-related representations, etc.). this results in precisely defining the interface contents to be developped and respected&nbsp;for each component. This implementation definition is fully explained and justified by the former functional description to which it is linked.
      </p>
      <p>
       The physical support of these communication and interface elements is also to be defined in terms of physical links that will carry them, and to which they will be allocated.
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/21963be2f5f544798045079ed00879fa.html">
       Define &amp; enforce a PBS and Component Integration Contract
      </a>
     </td>
     <td>
      <p>
       The definition of internal and external interfaces made in the 'Design Solution Architecture' activity is a major part of the contract towards sub-systems, software and hardware engineering. It should be elaborated in a collaborative manner between all engineering teams concerned, so as to integrate constraints of each team. Once approved, interfaces definition is the single and common reference for all stakeholders.
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/b4f96ce88e5d4a75a44982269ade639f.html">
       Perform Sub-System Engineering
      </a>
     </td>
     <td>
      <p>
       External interfaces of each sub-system should not be modified by the sub-system engineering team alone. If modifications are required, they should be collaborative, under responsibility of the system-level engineering team, along with other sub-systems, software, hardware engineering. Once a new reference interface definition is produced and validated by all stakeholders, it will be promoted and be imposed to all.
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/0f400333e4604c16a797eb161de26e50.html">
       Perform SW engineering
      </a>
     </td>
     <td>
      <p>
       External interfaces of each software component or sub-system should not be modified by the&nbsp;software engineering team alone. If modifications are required, they should be collaborative, under responsibility of the system-level engineering team, along with other sub-systems, software, hardware engineering. Once a new reference interface definition is produced and validated by all stakeholders, it will be promoted and be imposed to all.
      </p>
     </td>
    </tr>
    <tr>
     <td>
      <img alt="PhysicalFunction" src="../icon/PhysicalFunction.gif"/>
      <a href="../ARCADIA/e8a6129c560e4e5699f785edb67049e9.html">
       Perform HW &amp; mechanical engineering
      </a>
     </td>
     <td>
      <p>
       External interfaces of each hardware or mechanical component or sub-system should not be modified by the&nbsp;component engineering team alone. If modifications are required, they should be collaborative, under responsibility of the system-level engineering team, along with other sub-systems, software, hardware engineering. Once a new reference interface definition is produced and validated by all stakeholders, it will be promoted and be imposed to all.
      </p>
     </td>
    </tr>
   </table>
   <h2>
    Diagrams displaying "The Interface Trip"
   </h2>
   <ul>
    <li>
     <a href="../ARCADIA/acdab1064f694b2882a59b4a7fd9f8ca.html#_0unrwJT3Eeqxb5_tqwKmHg">
      3 - The Interface Trip*
     </a>
    </li>
   </ul>
  </div>
 </body>
</html>
